Hey @ai-virtual-b! Would it be better to have this in https://github.com/Virtual-Protocol/acp-python/tree/feat_client_examples/examples/acp_base? together with some add-ons in that readme

original idea was to that folder for "vanilla acp" example, and have other folders for other agent frameworks etc

also should we add browse_agent here?

I think we should check the socket connection before falling back to polling. Running both at once could cause the agent to receive duplicate instructions and double-sign the same memo for a single phase.

If the socket is connected but not emitting events, the issue is with the socket and should be fixed there — not bypassed by polling. Right now, polling is enabled regardless of socket status, but ideally, if the socket works, we shouldn’t poll at all.

wdyt?

Hey @Ang-dot - as discussed, I see polling vs websocket as alternative approaches so i think this is ok. Polling would be a "safe" alternative that is

• Less dependent on reliability of our sockets infra
• Easier to use as a job "backfill" or reconciliation option - say, if an agent fails to respond to job because of alchemy / websocket problems

Address comments with updated examples
Video Recording: https://drive.google.com/file/d/1SwwVL_yyBDM1zbcRTzRhvLuBCxHoRcyX/view?usp=drive_link